home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19990422-19990725
/
000171_news@watsun.cc.columbia.edu _Fri Jun 18 10:48:37 1999.msg
< prev
next >
Wrap
Internet Message Format
|
1999-07-23
|
3KB
Return-Path: <news@watsun.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id KAA27269
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 18 Jun 1999 10:48:37 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id KAA04177
for kermit.misc@watsun.cc.columbia.edu; Fri, 18 Jun 1999 10:40:42 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Subject: Re: Segmentation fault
Date: 18 Jun 1999 14:40:41 GMT
Organization: Columbia University
Message-ID: <7kdlp9$42e$1@newsmaster.cc.columbia.edu>
To: kermit.misc@watsun.cc.columbia.edu
In article <376A5489.674E7B8B@zkrd.de>,
Detlev Knorpp <Detlev.Knorpp@zkrd.de> wrote:
: Frank da Cruz wrote:
: > In article <376A41F5.FF6EA09D@zkrd.de>,
: > Detlev Knorpp <Detlev.Knorpp@zkrd.de> wrote:
: > : internal MultiTech MT5634ZPX (ISA) (I use modem type hayes-high-speed)
: > :
: > Why don't you "set modem type multitech"?
:
: many errors from the modem
:
You should report the errors so we can fix them.
Until now we have not heard about any problems with the built-in
Multitech modem type, which is based on a rather old model that
we had here. Maybe they have changed their command set in newer
models.
Do you have a command summary for your modem? Can you send it?
If it's on paper you can fax it to:
+1 212 662 6442
: > C-Kermit 7.0 Beta.07 on which Linux? Did you build it yourself? Did
: > you use one of the prebuilt binaries? Which one?
:
: I built it without any warnings or errors, and I tried the
: cku195b07_linux-i386-su6.0 binary package without any success
:
That's not a "package" (in the RPM sense); it's just a binary Kermit
executable. What happened when you tried to run it?
What was the difference in behavior between the one you built yourself
and the cku195b07.linux-i386-su6.0 version that you downloaded?
Unfortunately I do not have SuSE here (yes, I know I should get it, along
with 500 other operating systems) so I can't test this myself.
The SuSE binary was contributed by a SuSE 6.0 user, who is not having any
trouble with it.
Evidently there is some difference between your SuSE 6.0 system and his.
I wonder what it could be?
You said that this version dumps core when trying to transfer files, right?
And this happens when it is on the far end of the connection? That is, when
you make a connection TO the SuSE computer? So therefore this problem is
not related to curses.
Can you get a traceback from the core file?
$ cd <directory-where-core-file-is>
$ gdb <pathname-of-kermit-binary-that-crashed> core
(gdb) bt
(show me what it says here...)
(gdb) quit
$
- Frank